Well, the last beta roundup is here, and yes, it includes the new and improved ColdBox Dashboard. So please enjoy this beta as it includes the following updates and enhancements: - ColdBox Dashboard 2.0.0 - Welcome to ColdBox IoC Object Caching: You can now enable the IOC plugin to cache your service objects in the coldbox cache. In order to do this, you will have to enable it in your config file via the 'IOCObjectCaching' flag. Then, you will need to get rid of your singletons in your IOC declartion files and declare your singletons via the cfcomponet tag using the 'cache=true' metadata attribute. You can also assign a timeout here. - Caching Debugging Panel Enhanced. - Coldspring now receives the coldbox controller reference as part of the settings structure. The gap in the model is now closed. You can now reference the active coldbox controller in your IoC configuration files by using '${Setting: coldbox_controller not found}'. You will now be able to use the framework in your model objects if needed. - AppMapping setting in the config file is now optional. If set in the config file, then it will override the auto-detected mapping. This is a great feature if your main application root is not reachable from the url. - The new object to use in the event handler methods and layouts/views is 'Event' to standardize with conventions. - All documentation updated to 2.0.0 - BlueDragon fixes - Minor fixes,updates. - Install ANT task, so you can refactor the code if needed. - Application Template ANT task. You can now create new applications via ANT. - More guides coming soon. You can find the beta in the forums as usual Well, enjoy this latest beta as the release is coming soon.
Categories:
Archives:
Blog
Recent Entries
Into the Box 2025 Virtual Tickets Are Now LIVE!
The wait is over! By popular demand, Into the Box 2025 virtual tickets are officially available! Secure your spot today and take advantage of our exclusive early bird pricing before it’s gone!
We’re bringing the community together to push the boundaries of modern development—because change starts with us. We’ve taken the first step, now it’s your turn to evolve and take action!
Security Red Flags in Your ColdFusion App (and how to fix them!)
Security breaches can lead to data leaks, legal issues, and irreversible damage to your company's reputation. Many ColdFusion applications—especially older ones—are vulnerable to cyber threats due to outdated code, weak authentication, and improper security configurations.
When was the last time you audited your ColdFusion application for security risks? If you’re unsure, it’s time for a professional security review.
Top ColdFusion Security Risks – Are You Expose...
BoxLang 1.0.0 RC3 Has Landed!
We are thrilled to announce the release of BoxLang 1.0.0-RC.3, marking a significant milestone in the development of our dynamic JVM language. This release brings a major performance boost and over 100 bug fixes and improvements, making it our most robust release to date. We are now entering the final stretch towards our full release on May 1st, and we need your help to ensure everything is in perfect shape. Please test your applications and report any issues.
Add Your Comment
(2)
Mar 18, 2007 07:16:49 UTC
by Sana
Hi Luis, Its really great work, Would you like to explain one thing. below text from your post: [You will now be able to use the framework in your model objects if needed]. Thanks
Mar 18, 2007 12:06:31 UTC
by Luis Majano
Sure Sana, I can actually send the coldbox controller reference into a bean declaration by using the following property in coldspring: ${coldbox_controller} Once I receive the controller in the model objects I can use it and tap into the framework. Let's say I wanted a setting: coldbox_controller.getSetting("AppMapping") Let's say I wanted to use the AOP logging tool: coldbox_controller.getPlugin("logger").logEntry("info","I am logging from my model object")> Now, some people will say, then you tie your object model to a framework. Well, the answer is YES!! That is my purpose, to extend into the object model and take over. There are so many good things about it, I am using it anyways. So If I ever decide to go to another framework, probably means, ColdBox is not around anymore. So expect more object model infiltrations by coldbox.